From 39269a128c257047b3fe5f99e5169187cdd5e96f Mon Sep 17 00:00:00 2001
From: leavehouse <31998645+leavehouse@users.noreply.github.com>
Date: Thu, 21 Sep 2017 14:05:48 -0500
Subject: [PATCH] Clarify dependencies documentation

The snippet:

```
... but not `2.0`. `0.0.x` is not considered ...
```
Looks very similar to `... but not 2.0.0.0.x is not considered ...`, when rendered, which is confusing.

This adds a couple words to clarify.
---
 src/doc/book/src/reference/specifying-dependencies.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/doc/book/src/reference/specifying-dependencies.md b/src/doc/book/src/reference/specifying-dependencies.md
index ba7145d12..503dcd099 100644
--- a/src/doc/book/src/reference/specifying-dependencies.md
+++ b/src/doc/book/src/reference/specifying-dependencies.md
@@ -31,8 +31,8 @@ An update is allowed if the new version number does not modify the left-most
 non-zero digit in the major, minor, patch grouping. In this case, if we ran
 `cargo update -p time`, cargo would update us to version `0.1.13` if it was
 available, but would not update us to `0.2.0`. If instead we had specified the
-version string as `^1.0`, cargo would update to `1.1` but not `2.0`. `0.0.x` is
-not considered compatible with any other version.
+version string as `^1.0`, cargo would update to `1.1` but not `2.0`. The version
+`0.0.x` is not considered compatible with any other version.
 
 Here are some more examples of caret requirements and the versions that would
 be allowed with them:
-- 
2.30.2